Fix Telegram aiogram session compatibility - #13
Open
muqiao215 wants to merge 10 commits into
Open
Conversation
added 10 commits
May 17, 2026 13:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_TelegramPollingSessionwith current aiogram session interfacesProblem
On hosts with
transports=["feishu", "telegram"], Telegram transport startup could crash before the service came online after aiogram interface changes. In live impact, this caused ControlMesh user services to loop under systemd instead of serving the primary transport.Changes
_TelegramPollingSession.stream_content()by delegating to the wrapped aiogram session_TelegramPollingSession.make_request()to accept and forwardtimeout=instead of the oldrequest_timeout=positional pathrun_startup()from scheduling the removed_watch_polling_liveness()/_polling_watchdogpathValidation